Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1656

reference
795-tree-1
name
1656
tree-preservation-order

undefined

795-tpo-1
uprn
address-text
point
POINT (-1.037539 50.857900)
geometry
MULTIPOLYGON (((-1.037482 50.857894,-1.037485 50.857906,-1.037493 50.857916,-1.037505 50.857924,-1.037521 50.857929,-1.037538 50.857931,-1.037556 50.857929,-1.037572 50.857924,-1.037584 50.857916,-1.037593 50.857906,-1.037596 50.857895,-1.037593 50.857884,-1.037585 50.857874,-1.037573 50.857866,-1.037557 50.857861,-1.037540 50.857859,-1.037522 50.857861,-1.037506 50.857866,-1.037493 50.857873,-1.037485 50.857883,-1.037482 50.857894)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL